Changes as defined by MLAB-6185 #130
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
A preview of 3c7967d is uploaded and can be seen here: ✨ https://mevislab.github.io/examples/pull/130/ ✨ Changes may take a few minutes to propagate. Since this is a preview of production, content with |
|
|
||
| * **Show Internal Network:** [Macro modules](glossary/#macro-module) provide an entry to open the internal network. You can see what happens inside a macro module. The internal network may also contain other macro modules. | ||
| * **Show Window:** If a module does not provide a User Interface, you will see the automatic panel showing the module's name. Modules may additionally have one or more windows that can be opened. You can also open the Scripting Console of a module to integrate Python. | ||
| * **Show Internal Network:** [Macro modules](glossary/#macro-module) provide an entry to open the internal network. You can see what happens inside a macro module. The internal network may also contain other macro modules. Changes in the internal network are applied to the currently running instance of yor module but not saved permanently. |
| * **Reload Definition:** In the case you are currently working on a module, you may need to reload the definition so that your changes are applied on the module (for example, attached Python scripts). | ||
| * **Related Files:** Related files allows a quick access to the modules *.script* or *.py* files. The files are automatically opened in [MATE](glossary/#mevislab-mate) for editing. | ||
| * **Reload Definition:** In case you are currently working on a module, you may need to reload the definition so that your changes are applied on the module (for example attached Python scripts). | ||
| * **Related Files:** Related files allows a quick access to the modules *\*.script* or *\*.py* files. The files are automatically opened in [MATE](glossary/#mevislab-mate) for editing. Changes on the .mlab file are applied permanently for your module. |
Contributor
There was a problem hiding this comment.
*\*.script* / *\*.py* has been intentionally removed by the previous change. Probably also use *.mlab*.
| internal network of your macro module. Now you are able to open the panel of | ||
| the module `LocalImage`. Right-click {{< mousebutton "right" >}} the desired field: In this case, right-click the label | ||
| *Name:*. Select *Copy Name*, to copy the internal name of this field. | ||
| the image, we like to create CSOs from. This functionality is already given in the internal network in the module `LocalImage`. We can copy this functionality from `LocalImage` and add this option to the panel above both viewers. But, how should we know, which field name we reference to? To find this out, open the network file of your macro module again. Now you are able to open the panel of the module `LocalImage`. Right-click {{< mousebutton "right" >}} the desired field: In this case, right-click the label *Name:*. Select *Copy Name*, to copy the internal name of this field. |
Contributor
There was a problem hiding this comment.
already given -> already present
|
|
||
|  | ||
|
|
||
| If you want to change the permanent behaviour or the module, right-click {{< mousebutton "right" >}} and select {{< menuitem "Related Files" "Filter.mlab" >}}. The network file of the module opens. Changes applied in this file are saved permanently. |
Contributor
There was a problem hiding this comment.
behavior (US-english)
applied in this file -> to this file
| * Modules can be clustered. Clustered modules can be encapsulated into local or global macro modules. | ||
| * Macro modules encapsulate networks. Internal networks can be shown and modified. Any changes of the internal network are applied to the macro module. | ||
| * Macro modules encapsulate networks. Internal networks can be shown and modified. Any changes of the internal network are applied to the macro module on the fly, changes in the *.mlab file are changing the permanent behaviour of your module. | ||
|
|
Contributor
There was a problem hiding this comment.
*.mlab -> *.mlab*
are changing -> change
behaviour -> behavior
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.